Hi David,

I'm guessing what might be happening is that motion is in progress and someone or something causes a feedhold to stop motion.  If you then do something like restart the application or start another application and release the feedhold then motion may continue.  Commanding a Halt, Stop or other error that disables any Coordinated Motion Axis should clear any motion and feedhold.  But if none of these occurs then the feedhold condition may persist in a resume-able state.  Adding:

    ClearStopImmediately();

to your initialization file may help.

Regards

TK

---

From: "david.m.stevenson@... [DynoMotion]" <DynoMotion@yahoogroups.com>
To: DynoMotion@yahoogroups.com
Sent: Friday, August 8, 2014 9:09 AM
Subject: [DynoMotion] Clearing the KFlop Memory

 

Hi Tom,

When a machine is working and gets halted by unusual means, the motion command remains in the memory of the KFlop, I believe, until the card is power cycled.

Is there a command which could be added to the initialization file which would clear any old motion commands if the operator forgot to power cycle the card?

Thank you,
David.

 

Hi David,

It may.  A little different scenario than what I described.  If the system is in Feedhold it is basically being continuously commanded to one spot.  If you then do something like a Home or Jog to move an axis there will be a conflict where the axis is constantly commanded to two different places.  I'm not sure who would "win".  After the homing stops the axis might jump back to the Feedhold position.

In any case adding the call to ClearStopImmediately(); in your Initialize Program and Home Program should solve the problem.  Please try it.

Regards

TK

---

From: "David Stevenson david.m.stevenson@... [DynoMotion]" <DynoMotion@yahoogroups.com>
To: DynoMotion@yahoogroups.com
Sent: Sunday, August 10, 2014 3:36 AM
Subject: Re: [DynoMotion] Clearing the KFlop Memory

 

Hi Tom,

My understanding is the operator stops the system in the middle of a motion command, by some means, and they are then homing the machine and once the homing takes place and the axis re-enable the machine takes off running. I believe the runaway is because of a previous motion command.

Does this make sense?

Thanks,
David.

On 8/9/2014 9:06 PM, Tom Kerekes tk@... [DynoMotion] wrote:

 

Hi David,

I'm guessing what might be happening is that motion is in progress and someone or something causes a feedhold to stop motion.  If you then do something like restart the application or start another application and release the feedhold then motion may continue.  Commanding a Halt, Stop or other error that disables any Coordinated Motion Axis should clear any motion and feedhold.  But if none of these occurs then the feedhold condition may persist in a resume-able state.  Adding:

    ClearStopImmediately();

to your initialization file may help.

Regards

TK

---

From: "david.m.stevenson@... [DynoMotion]" <DynoMotion@yahoogroups.com>
To: DynoMotion@yahoogroups.com
Sent: Friday, August 8, 2014 9:09 AM
Subject: [DynoMotion] Clearing the KFlop Memory

 

Hi Tom,

When a machine is working and gets halted by unusual means, the motion command remains in the memory of the KFlop, I believe, until the card is power cycled.

Is there a command which could be added to the initialization file which would clear any old motion commands if the operator forgot to power cycle the card?

Thank you,
David.